home *** CD-ROM | disk | FTP | other *** search
Text File | 1990-04-06 | 1.7 KB | 45 lines | [TEXT/GEOL] |
- Item forwarded by FRED.FORSMAN to RUSS.DANIELS PAULSON3
-
- Item forwarded by A33 to A34
-
- Item 7648364 2-April-90 20:30PDT
-
- From: D5780 Stat-Ease, Robert Altman,PRT
-
- To: RANSON France - Dev, Ranson Lannion,IDV
-
- cc: MACAPP.TECH$ MacApp Technical
-
- Sub: SADE and MacApp
-
- Daniel,
-
- In regards to your question about SADE and MacApp:
-
- - SADE does not seem to work with Virtual2.0. It most of the time cannot
- associate a PC with a source statement. (For that matter, MacsBug6.2d5 doesn't
- work much better).
- -- Neither SADE nor Macsbug is 32 bit clean. They cannot "point" at a program
- loaded above the 8 Meg system limit. If you use Virtual to make your Mac into
- an 8 Meg machine, then they will work. However, real memory will work faster.
- This is mentioned in Virtual's release notes (if memory serves).
-
-
- - Without Virtual, it does work, but sometimes SADE breaks into Macsbug with
- a message: "Patch to checkLoad got an unrecognized or 0 pid!!". As far as I
- can remember, all occurences were when I tried to step over UnloadAllSegments.
- I can reproduce the problem 100% of the times by stepping the "New" menu
- command in the Nothing example.
- -- Can't help here. I have not seen this problem.
-
- -- Additional Info. Look at Jasik's Debugger. It's faster than SADE when
- stepping through code, handles MacApp well, includes Jasik's Incremental Build
- System (IBS), and is a lot of fun to use. Disadvantage: Difficult to set up
- and start with. However, the more you use it, the better you like it.
-
- Robert D. Altman
- Stat-Ease, Inc.
- Minneapolis, MN
-
-
-